Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1285

reference
390-tree-1
name
1285
tree-preservation-order

undefined

390-tpo-1
uprn
address-text
point
POINT (-1.025982 50.883960)
geometry
MULTIPOLYGON (((-1.025869 50.883948,-1.025874 50.883971,-1.025889 50.883991,-1.025914 50.884007,-1.025946 50.884017,-1.025981 50.884021,-1.026016 50.884018,-1.026048 50.884008,-1.026073 50.883992,-1.026090 50.883972,-1.026096 50.883950,-1.026091 50.883928,-1.026075 50.883908,-1.026050 50.883892,-1.026019 50.883881,-1.025984 50.883877,-1.025949 50.883881,-1.025917 50.883891,-1.025891 50.883906,-1.025875 50.883926,-1.025869 50.883948)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL